PeopleSoft Application Update Installation Instructions
This document discusses the contents of this application update, and the events
which will occur in your PeopleSoft application environment when the update is
applied. The objects delivered in this resolution update may include changes
to batch files, data changes, database code revisions and objects,
record structures, or PeopleCode. In addition, supplemental documents providing additional information pertaining to this resolution can be found under the <PS_HOME>\maint directory.
This document is intended for the expert technical user who is responsible for
applying application changes to your PeopleSoft system. This user should have
a basic understanding of PeopleSoft systems and have completed the PeopleSoft
Upgrade and Data Management training course. Familiarity with PeopleSoft
Upgrade Assistant, PeopleSoft Data Mover, PeopleSoft Application Designer,
COBOL compilers, and structure query language (SQL) tools may also be necessary.
For the latest information on updates and fixes for PeopleSoft applications,
see Customer Connection, PeopleSoft online information resource. Access
Customer Connection through PeopleSoft website at www.peoplesoft.com.
Important!
We recommend that you follow the instructions in the PeopleSoft Application Update Installation Guide when you apply an application update project to your database. Failure to do so could corrupt your database and cause you to lose customizations that you have made to your database.
General Information on Installing Application Updates
We recommend that you first install this update to your vanilla database
(for example, xxDMO) and thoroughly test it before you apply it to your
production databases.
We recommend that you run the Upgrade Comparison report against your DMO, test
production copy, and production databases to identify any changes delivered in
this application update that may impact any customizations that you have made
to your databases.
Installing an Update for Applications Using PeopleTools 8.44 and Beyond
Contents of This Update
Update ID: 597842
Subject: Enterprise Components Common Address bundle 1 2005
Description: IMPORTANT NOTE: This resolution contains the PRJ581982 project and related files.
Enterprise Components Common Address bundle 1 2005
Please see the supplemental documents in the UPD597842_install folder for details on the updates included in this bundle.
Note: Please refer to the excel worksheet that includes a list
of the objects and programs that will be modified in this update, as
well as a list of records included in this update along with the
appropriate actions for each. Note that if there is no X in the
update action column for a record, then no build action is required
for that record.
This chapter lists the project that will be applied by Change Assistant to
your database using Application Designer. Objects defined
in the project are PeopleTools managed objects such as Records, Fields, Pages,
Components, PeopleCode, etc.
This Change Package also contains PeopleTools non-managed objects such as
Access Groups, Cube Definitions, Cube Instances Definitions, Dimensions, Message
Catalogs, Roles, and Tree definitions. These objects will be applied to
your database
via Data Mover script(s) in this Change Package.
Task: Apply Non Managed MetaData
Change Assistant will execute Data Mover script(s) to update non-managed metadata
in your database.
Step: Import Message Catalog Definitions
This script will update the Message Catalog definitions in your database:
upd597842_msg_i.dms
upd597842_msg.dat
PRJ581982
Step: Compare Project with Source Database
First step in the migration of a PeopleSoft-delivered change package to
your environments. PeopleSoft Change Assistant runs a compare
report of the project between a PeopleSoft demo database that
contains this project and your target database.
Manual Step: Examine Compare Report
After the project compare completes,
examine the report and decide whether or not to
accept the object change.
1. Using Application Designer, modify the
actions for each of the
objects in the source database.
2. Within PeopleSoft Change Assistant, mark this step
Complete or you cannot
continue with the migration process.
Note: PeopleSoft does not support the addition or removal of objects
through the migration process.
Step: Copy Project From Source Database
PeopleSoft Change Assistant copies the project from your source database to
your target database, based on the object actions you specified in the
previous step.
Step: Extract Change Package
Peoplesoft Change Assistant extracts the change package to a temporary directory
in your staging directory (~ExtractedCP).
Manual Step: Re-Apply Your Customizations
After the project has been copied to your target database,
re-apply your customizations in your target database using
Application Designer.
Step: Export Project From Target Database
PeopleSoft Change Assistant exports the project, including your customizations,
from the target database to a temporary directory in the staging directory
(~ExportedProject).
Step: Create Modified Change Package
PeopleSoft Change Assistant creates a modified change package that includes
your customizations.
Step: Copy Update Project
This step will update your PeopleSoft object definitions.
Chapter: Execute File References
This chapter lists the program(s) or script(s) that will be executed against
your database.
Chapter: Deploy Files
This chapter lists files in the Change Package that were 'File Reference'
objects marked for deploy. The files will be copied into the locations that are
associated with their corresponding File Type Codes on your database.
The chapter also lists the COBOL files which should be deployed and compiled,
if there are any.
Task: File Type Code: MAINT
Change Assistant will deploy the following files to the appropriate PeopleSoft server(s):
upd581982_1.dat
upd581982_1_i.dms
upd581982_2.dat
upd581982_2_i.dms
Task: Copy File(s) For OS390
You must manually FTP files included in this Change Package from your batch or file
server to the OS/390 PDS. Here are the PDS file locations based on type of file:
ASM files go into $PSHLQ$.SRCLIB
CBL(which are not copy lib) files go into $PSHLQ$.SRCLIB
CBL (which are copy lib) files go into $PSHLQ$.COPYLIB
SQL files go to $PSHLQ$.DDLLIB
JCL files go to $PSHLQ$.JCLLIB
PRC files go to $PSHLQ$.PROCLIB
SQR files go to $PSHLQ$.SQRSRC
SQC files go to $PSHLQ$.SQRINC
PAR files go to $PSHLQ$.PARMLIB
Chapter: Build And Alter
Change Assistant will modify the database structure as necessary:
Tables may be dropped
Tables may be created
Tables may be altered
Triggers may be created
Views may be created
Indexes may be created
Conversion script(s) may be executed
Task: Build and Alter
Change Assistant will modify the database structure as necessary:
Tables may be dropped
Tables may be created
Tables may be altered
Triggers may be created
Views may be created
Indexes may be created
Step: Build and Alter Step
This step will create SQL scripts for database structure changes.
Step: Run Create Tables Script
This step will execute table creation SQL scripts against your database.
Step: Run Alter Tables Script
This step will execute alter table SQL scripts against your database.
Step: Run Create Triggers Script
This step will execute trigger creation SQL scripts against your database.
Step: Run Create Views Script
This step will execute view creation SQL scripts against your database.
Step: Run Create Indexes Script
This step will execute index creation SQL scripts against your database.
Chapter/Task: Update Package Prerequisites
Prerequisite information is retrieved from the Change Package and
Project prerequisites are updated in your database.
